Subject: VZLAQ-MASTER — what's in the package, and how to refresh the data

Hi,

Attached is VZLAQ-MASTER.md and the files it works from. This note explains what each file is, which ones go stale, and how to refresh them yourself if you want current data before a session.

WHAT'S INCLUDED

The instance runs in three phases, each on its own set of files:

Phase 1 — Document register
  OFACbatch_001.md            OFAC General Licenses, E.O.s, Federal Register notices
  Gacetabatch_001.md, _002, _003   Gaceta Oficial 2026, three batches
  TSJbatch_001.md             Tribunal Supremo de Justicia decisions
  framework.txt               31 CFR 591 and the E.O. stack — reference, never extracted
  OFAC_Template.md, Gaceta_Template.md   the two original specs, superseded; keep for traceability

Phase 2 — Commentary and thesis
  cash35.md                   the research memorandum (v35, 18 July 2026). The instance reads this in full and cross-references everything against it
  TimeLINe_13.md              the master timeline, v13
  Q-ANALYTICAL-SPEC-v3.md and HANDOVER-Q-ANALYTICAL-06SEP2026.md   superseded, keep for traceability

Phase 3 — Rate series
  yadio.csv                   parallel rate, 5-minute bars, MetaStock format, UTC. As sent: 6 Mar – 5 Sep 2026
  BCV_float.csv               official BCV rate, daily. This is the file the older spec called BCV_Metastock.csv — same file, new name. Note the values are in raw units (VED × 1,000,000); the instance knows this
  tasas_sistema_bancario_full.html   per-bank compra/venta panel from the BCV. AS SENT THIS FILE IS NOT UP TO DATE — it ends 14 August 2026. See below for how to refresh it
  fetchdata.xlsm              Excel refresh tool — see below
  Q-NUMERICAL-SPEC-v3.md      superseded, keep for traceability

Upload everything at once. The spec tells the instance which files belong to which phase and in what order to work.

WHICH FILES GO STALE

The Phase 1 and Phase 2 files are batches — they are what they are until a new batch is cut. The three Phase 3 files are live series and will be out of date within a day or two. If you're running a session on current market conditions, refresh those three first.

REFRESHING THE RATE SERIES

BCV_float.csv is published live at:
  https://dnsxv.com/BCV_float.csv
Download it in a browser and replace the attached copy. Nothing else to do.

fetchdata.xlsm is a small Excel workbook with six macros, one per tab. Open it, enable macros when Excel asks, and press:

  Ctrl+Q, Ctrl+W, Ctrl+E, Ctrl+R, Ctrl+T, Ctrl+Y

Each key runs one fetch and fills one tab:
  Import            latest parallel prints from the Yadio API
  BCV float         last 10 rows of BCV_float.csv
  Parallel D        last 10 rows of the daily parallel series
  Brecha 1 hour     hourly brecha bars, last 10 days
  Brecha 30         30-minute brecha bars, last 10 days
  Brecha Metastock  last 10 rows of the daily brecha series

(The key-to-tab mapping is set inside the workbook — Alt+F8, select a macro, Options, shows which key runs which. If you're unsure, run all six; each one clears and rewrites only its own tab.)

Two things to know about the tool:
  1. It writes only the most recent rows (the last 10 rows or last 10 days) to each tab. It is a "what's the latest" tool, not a full-history download. For full history use yadio.csv and BCV_float.csv.
  2. If you want the instance to see the refreshed figures, save the workbook and upload it. The instance will treat each tab as a short tail of recent data, not as a series.

REFRESHING THE BANK PANEL (tasas_sistema_bancario_full.html)

This one has to be done by hand, and there is a formatting step the LLM depends on:

  1. Go to https://www.bcv.org.ve/tasas-informativas-sistema-bancario
  2. Download the .xls file the BCV offers.
  3. Rename the file, changing the extension from .xls to .html
     (the BCV's "xls" is actually an HTML table; the LLM reads it correctly only with the .html extension).
  4. Name it tasas_sistema_bancario_full.html and upload it in place of the attached one.

If you don't refresh it, the instance will still run — it will just tell you the panel is stale and won't compute panel statistics for sessions the file doesn't cover.

Any questions on the files, ask. On the spec itself, the instance will explain its own phases if you ask it.

The initial setup may pushback because of size, if it does tell it to "Follow the original Specification"

Happy researching!